Labels:text | screenshot | font | line | parallel | number | diagram | document OCR: vol_gp table sum_ jostat table mount point vol_grp mount_point samp_date hdisk mount point elapsed. seconds mount_point mount_point k_read k_write files tat table hasl samp_date elapsed.seconds sum_filestat table mount point iostat table tablespace_name samp_date file_name samp_date mount point elapsed. seconds elapsed. seconds phys_reads phys_blks_rd bdisk phys-blks_rd phys_rd_time k_read phys_rd_time phys_writes k_write phys_blks_wr phys_blks_wr phys_wrt_tim phys_wrt_tim FIGURE 3: Several summary tables work together to help in the load-balancing process: After poplulating the vol grp table with information about mount points and their associated disks, you can relate the disk-level data to the file-level data and identify which files are causing excessive activity on a disk. You can easily create summary tables such as sum iostat and sum_filestat (which aggregate the disk- and file-level data by mount point) from the vol grp, filestat, and iostat tables.
(2000).iso/oracl/9b1/burlf103.gif){kind=small}
(2000).iso/oracl/9b1/burlf102.gif){kind=link}
(2000).iso/oracl/9b1/coucf102.gif){kind=link}